-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add EIP-5748: Approval Expiration for EIP-20 Tokens #5748
Conversation
Hi! I'm a bot, and I wanted to automerge your PR, but couldn't because of the following issue(s): (fail) eip-5748.md
(pass) assets/eip-5748/eip-5748.sol
|
Hey lucky, I’m still getting up to speed on the language and adaptability on how to use in my projects. Please excuse my absence. If you have any tips on how to catch up as fast as I can, please advise
…Sent from my iPhone
On Oct 4, 2022, at 8:34 AM, eth-bot ***@***.***> wrote:
Hi! I'm a bot, and I wanted to automerge your PR, but couldn't because of the following issue(s):
(fail) EIPS/eip-draft_erc20_approval_expiration.md
classification
ambiguous
file 'EIPS/eip-draft_erc20_approval_expiration.md' is not a valid eip file name; all eip files need to be in eip-####.md format. It's assumed however that this has been included because an eip number has not been provided for this eip yet. cc @***@***.******@***.******@***.******@***.***
(fail) assets/eip-draft_erc20_approval_expiration/erc20-approval-expiration.sol
classification
ambiguous
'assets/eip-draft_erc20_approval_expiration/erc20-approval-expiration.sol' must be in eip-###.md format; this error will be overwritten upon relevant editor approval
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
eip: <to be assigned> | ||
title: Approval Expirations for ERC20 Tokens | ||
description: This standard introduces a standardized way for users to set expiration limits on ERC-20 token approvals. | ||
author: Go+ Security <@GoPlusSecurity>, Jeff Hall <@JeffHal25193696>, Xavi <@XaaaaavitheFool>, Turan Vural <@turanzv> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Github names need to be wrapped in parentheses like this lightclient (@lightclient)
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be reviewed. There is a problem between the account and management account is being reviewed
Approval Expirations for ERC20 Tokens -> Approval Expiration for ERC-20 Tokens Co-authored-by: lightclient <[email protected]>
Co-authored-by: lightclient <[email protected]>
@lightclient we're hitting CI failures with the "EIP Walidator". Our references to ERC-20 are being flagged as violations. Should we be referring to ERC-20 as EIP-20? |
Co-authored-by: Sam Wilson <[email protected]>
Co-authored-by: Sam Wilson <[email protected]>
Co-authored-by: Sam Wilson <[email protected]>
Co-authored-by: Sam Wilson <[email protected]>
Co-authored-by: Sam Wilson <[email protected]>
Co-authored-by: Sam Wilson <[email protected]>
This comment was marked as spam.
This comment was marked as spam.
assets/eip-5748/eip-5748.sol
Outdated
@@ -0,0 +1,557 @@ | |||
// SPDX-License-Identifier: MIT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Must be CC0.
refactor and adding interface
|
||
So that existing event statistics are not perturbed by the implementation of this standard, `_approve()` is triggered by the new event `AllowanceExpireTimeUpdated()`. | ||
|
||
This standard is absolutely compatible with the traditional [EIP-20](./eip-20.md) standard. `DEFAULT_EXPIRATION` is added so that the original `approve(address spender, uint256 amount)` method header can remain for backwards compatibility and ease of programming. `DEFAULT_EXPIRATION` can be set to a constant or variable according to the developer's needs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we know this is 'absolutely compatible' ?
|
||
## Abstract | ||
|
||
This standard adds an expiration time to the `_approve()` function of token contracts to automatically recall approvals within a certain time period. This functionality as a standard will prevent vulnerabilty exploits due to outstanding token approvals. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where is this _approve
coming from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect _approve
comes from a well known EIP-721 implementation? The standard itself doesn't define it.
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
This pull request was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment. |
Should be reviewed. There is a problem between the account and management account is being reviewed |
When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md
We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met: